home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19990725-20000114
/
000435_news@columbia.edu _Mon Jan 10 20:24:16 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id UAA14321
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 10 Jan 2000 20:24:16 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id UAA18185
for kermit.misc@watsun.cc.columbia.edu; Mon, 10 Jan 2000 20:15:55 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Subject: Re: Question on ckermit 7 redirect in background
Date: 11 Jan 2000 01:15:54 GMT
Organization: Columbia University
Message-ID: <85e08a$ho7$1@newsmaster.cc.columbia.edu>
To: kermit.misc@columbia.edu
In article <387A77D7.52E5B806@matsch.com>,
Charlie Sears <charlie@matsch.com> wrote:
: I would like to use kermit to read ascii text from a serial port and
: dump the text into a file (or pipe it to another command). I need to
: run the entire process in the background so it can start automatically
: when an unattended system boots.
:
: I considered using the connect command and piping the output, but this
: doesn't work in the background:
: # nohup kermit -l /dev/ttyS0 -b 9600 -B -C "c" > file 2>&1 &
: [1] 1131
: #
: [1]+ Stopped (tty output) nohup kermit -l /dev/ttyS0 -b 9600 -B -C
: "c" >file 2>&1
:
: The redirect command also works fine when running kermit interactively,
: but when running in the background no data is written to the file. Any
: thoughts would be appreciated.
:
: This is using C-Kermit 7.0.196 Beta.11, 6 Dec 1999, for Linux (RedHat).
:
First grab the final 7.0 release:
http://www.columbia.edu/kermit/ckermit.html
Then code your application as a kerbang script:
http://www.columbia.edu/kermit/ckermit.html#studies
Don't enter CONNECT mode. Use LOG SESSION for recording and then INPUT to
wait for (a) the desired amount of time, (b) a string that should terminate
logging, or (c) forever. To log forever, use INPUT -1 XXXXX, where "XXXXX"
is a string that will never come.
- Frank